chore(python): drop EOL Python 3.9 and 3.10 support#14
Merged
Conversation
Python 3.9 reached end-of-life on 2025-10-31 and 3.10 is scheduled for EOL in 2026-10 per devguide.python.org. The CI matrix already only tested 3.11-3.14, so the >=3.9 claim in pyproject.toml was never actually verified. Bump requires-python to >=3.11 so the declared support matches the CI matrix, and drop the 3.9 / 3.10 trove classifiers. Closes #10
Changepacksdependency-check-updates@0.1.6 → 0.2.0 - bridge/python/pyproject.tomlMinor
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes #10.
Python 3.9 reached end-of-life on 2025-10-31 per devguide.python.org. 3.10 is already in security-only mode and hits EOL in 2026-10.
Meanwhile the project's CI matrix only tests
3.11/3.12/3.13/3.14, so theequires-python = ">=3.9" claim in
bridge/python/pyproject.tomlwas never actually verified — it was a documentation lie.Changes
bridge/python/pyproject.toml: bumprequires-pythonfrom>=3.9to>=3.11; drop the3.9and3.10trove classifiers.README.md: update the Python badge and the Development prerequisites from3.9+to3.11+..changepacks/changepack_log_*.json: Minor-version bump forbridge/python/pyproject.tomldocumenting the drop.Why 3.11 (not 3.10)
3.11/3.12/3.13/3.14only; aligning declared support with what we actually test avoids a repeat of the>=3.9situation.Verification
cargo clippy --all-targets --all-features -- -D warnings— cleancargo test --workspace— 57 passed, 0 failedcargo fmt --check— cleanImpact
Pure packaging metadata change — no Rust / Node code is touched. Existing users on Python 3.9 / 3.10 will get a clear
pipresolver error instead of a silently broken wheel.